-- Network Working Group A. Siddiqui
-- Request for Comments: 4712 D. Romascanu
-- Category: Standards Track Avaya
-- E. Golovinsky
-- Alert Logic
-- M. Rahman
-- Samsung Information Systems America
-- Y. Kim
-- Broadcom
-- October 2006-- Transport Mappings for Real-time Application Quality-of-Service
-- Monitoring (RAQMON) Protocol Data Unit (PDU)RAQMON-RDS-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,NOTIFICATION-TYPE,Counter32,Unsigned32FROM SNMPv2-SMI
DateAndTimeFROM SNMPv2-TC
rmon
FROM RMON-MIB
SnmpAdminStringFROM SNMP-FRAMEWORK-MIB
InetAddressType,InetAddress,InetPortNumberFROM INET-ADDRESS-MIB
DscpFROM DIFFSERV-DSCP-TC
MODULE-COMPLIANCE,OBJECT-GROUP,NOTIFICATION-GROUPFROM SNMPv2-CONF;raqmonDsMIB MODULE-IDENTITYLAST-UPDATED"200610100000Z"-- October 10, 2006ORGANIZATION"RMON Working Group"CONTACT-INFO"WG EMail: rmonmib@ietf.org
Subscribe: rmonmib-request@ietf.org
MIB Editor:
Eugene Golovinsky
Postal: BMC Software, Inc.
2101 CityWest Boulevard,
Houston, TX, 77094
USA
Tel: +713-918-1816
Email: egolovin@bmc.com
"DESCRIPTION"This is the RAQMON Data Source notification MIB Module.
It provides a mapping of RAQMON PDUs to SNMP
notifications.
Ds stands for data source.
Note that all of the object types defined in this module
are accessible-for-notify and would consequently not be
available to a browser using simple Get, GetNext, or
GetBulk requests.
Copyright (c) The Internet Society (2006).
This version of this MIB module is part of RFC 4712;
See the RFC itself for full legal notices."REVISION"200610100000Z"-- October 10, 2006DESCRIPTION"Initial version, published as RFC 4712."::={ rmon 32}-- This OID allocation conforms to [RFC3737]raqmonDsNotifications OBJECTIDENTIFIER::={ raqmonDsMIB 0}raqmonDsMIBObjects OBJECTIDENTIFIER::={ raqmonDsMIB 1}raqmonDsConformance OBJECTIDENTIFIER::={ raqmonDsMIB 2}raqmonDsNotificationTable OBJECT-TYPESYNTAXSEQUENCEOF RaqmonDsNotificationEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"This conceptual table provides the SNMP mapping of
the RAQMON BASIC PDU. It is indexed by the RAQMON
Data Source, sub-session, and address of the peer
entity.
Note that there is no concern about the indexation of
this table exceeding the limits defined by RFC 2578
Section 3.5. According to [RFC4710], Section 5.1,
only IPv4 and IPv6 addresses can be reported as
participant addresses."::={ raqmonDsMIBObjects 1}raqmonDsNotificationEntry OBJECT-TYPESYNTAX RaqmonDsNotificationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry (row) is not retrievable and is not kept by
RDSs. It serves data organization purposes only."
INDEX{ raqmonDsDSRC, raqmonDsRCN, raqmonDsPeerAddrType,
raqmonDsPeerAddr }::={ raqmonDsNotificationTable 1}
RaqmonDsNotificationEntry ::=SEQUENCE{
raqmonDsDSRC Unsigned32,
raqmonDsRCN Unsigned32,
raqmonDsPeerAddrType InetAddressType,
raqmonDsPeerAddr InetAddress,
raqmonDsAppName SnmpAdminString,
raqmonDsDataSourceDevicePort InetPortNumber,
raqmonDsReceiverDevicePort InetPortNumber,
raqmonDsSessionSetupDateTime DateAndTime,
raqmonDsSessionSetupDelay Unsigned32,
raqmonDsSessionDuration Unsigned32,
raqmonDsSessionSetupStatus SnmpAdminString,
raqmonDsRoundTripEndToEndNetDelay Unsigned32,
raqmonDsOneWayEndToEndNetDelay Unsigned32,
raqmonDsApplicationDelay Unsigned32,
raqmonDsInterArrivalJitter Unsigned32,
raqmonDsIPPacketDelayVariation Unsigned32,
raqmonDsTotalPacketsReceived Counter32,
raqmonDsTotalPacketsSent Counter32,
raqmonDsTotalOctetsReceived Counter32,
raqmonDsTotalOctetsSent Counter32,
raqmonDsCumulativePacketLoss Counter32,
raqmonDsPacketLossFraction Unsigned32,
raqmonDsCumulativeDiscards Counter32,
raqmonDsDiscardsFraction Unsigned32,
raqmonDsSourcePayloadType Unsigned32,
raqmonDsReceiverPayloadType Unsigned32,
raqmonDsSourceLayer2Priority Unsigned32,
raqmonDsSourceDscp Dscp,
raqmonDsDestinationLayer2Priority Unsigned32,
raqmonDsDestinationDscp Dscp,
raqmonDsCpuUtilization Unsigned32,
raqmonDsMemoryUtilization Unsigned32}raqmonDsDSRC OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Data Source identifier represents a unique session
descriptor that points to a specific session
between communicating entities. Identifiers unique for
sessions conducted between two entities are
generated by the communicating entities. Zero is a
valid value, with no special semantics."::={ raqmonDsNotificationEntry 1}raqmonDsRCN OBJECT-TYPE
SYNTAXUnsigned32(0..15)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The Record Count Number indicates a sub-session
within a communication session. A maximum number of 16
sub-sessions are supported; this limitation is
dictated by reasons of compatibility with other
transport protocols."::={ raqmonDsNotificationEntry 2}raqmonDsPeerAddrType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION
"The type of the Internet address of the peer participant
for this session."REFERENCE"Section 5.2 of [RFC4710]"::={ raqmonDsNotificationEntry 3}raqmonDsPeerAddr OBJECT-TYPESYNTAXInetAddressMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The Internet Address of the peer participant for this
session."REFERENCE"Section 5.2 of [RFC4710]"::={ raqmonDsNotificationEntry 4}raqmonDsAppName OBJECT-TYPESYNTAXSnmpAdminString
MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This is a text string giving the name and possibly the
version of the application associated with that session,
e.g., 'XYZ VoIP Agent 1.2'."REFERENCE"Section 5.28 of [RFC4710]"::={ raqmonDsNotificationEntry 5}raqmonDsDataSourceDevicePort OBJECT-TYPESYNTAXInetPortNumberMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The port number from which data for this session was sent
by the Data Source device."
REFERENCE"Section 5.5 of [RFC4710]"::={ raqmonDsNotificationEntry 6}raqmonDsReceiverDevicePort OBJECT-TYPESYNTAXInetPortNumberMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The port number where the data for this session was
received."REFERENCE"Section 5.6 of [RFC4710]"::={ raqmonDsNotificationEntry 7}raqmonDsSessionSetupDateTime OBJECT-TYPESYNTAXDateAndTimeMAX-ACCESSaccessible-for-notify
STATUScurrentDESCRIPTION"The time when session was initiated."REFERENCE"Section 5.7 of [RFC4710]"::={ raqmonDsNotificationEntry 8}raqmonDsSessionSetupDelay OBJECT-TYPESYNTAXUnsigned32(0..65535)UNITS"milliseconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Session setup time."REFERENCE"Section 5.8 of [RFC4710]"
::={ raqmonDsNotificationEntry 9}raqmonDsSessionDuration OBJECT-TYPESYNTAXUnsigned32UNITS"seconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Session duration, including setup time. The SYNTAX of
this object allows expression of the duration of sessions
that do not exceed 4660 hours and 20 minutes."REFERENCE"Section 5.9 of [RFC4710]"::={ raqmonDsNotificationEntry 10}raqmonDsSessionSetupStatus OBJECT-TYPESYNTAXSnmpAdminString
MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Describes appropriate communication session states, e.g.,
Call Established successfully, RSVP reservation
failed, etc."REFERENCE"Section 5.10 of [RFC4710]"::={ raqmonDsNotificationEntry 11}raqmonDsRoundTripEndToEndNetDelay OBJECT-TYPESYNTAXUnsigned32UNITS"milliseconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Most recent available information about the
round-trip end-to-end network delay."REFERENCE"Section 5.11 of [RFC4710]"::={ raqmonDsNotificationEntry 12}raqmonDsOneWayEndToEndNetDelay OBJECT-TYPESYNTAXUnsigned32UNITS"milliseconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Most recent available information about the
one-way end-to-end network delay."REFERENCE"Section 5.12 of [RFC4710]"::={ raqmonDsNotificationEntry 13}raqmonDsApplicationDelay OBJECT-TYPE
SYNTAXUnsigned32(0..65535)UNITS"milliseconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Most recent available information about the
application delay."REFERENCE"Section 5.13 of [RFC4710"::={ raqmonDsNotificationEntry 14}raqmonDsInterArrivalJitter OBJECT-TYPESYNTAXUnsigned32(0..65535)UNITS"milliseconds"
MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"An estimate of the inter-arrival jitter."REFERENCE"Section 5.14 of [RFC4710]"::={ raqmonDsNotificationEntry 15}raqmonDsIPPacketDelayVariation OBJECT-TYPESYNTAXUnsigned32(0..65535)UNITS"milliseconds"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"An estimate of the inter-arrival delay variation."
REFERENCE"Section 5.15 of [RFC4710]"::={ raqmonDsNotificationEntry 16}raqmonDsTotalPacketsReceived OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The number of packets transmitted within a communication
session by the receiver since the start of the session."REFERENCE"Section 5.16 of [RFC4710]"::={ raqmonDsNotificationEntry 17}raqmonDsTotalPacketsSent OBJECT-TYPE
SYNTAXCounter32UNITS"packets"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The number of packets transmitted within a communication
session by the sender since the start of the session."REFERENCE"Section 5.17 of [RFC4710]"::={ raqmonDsNotificationEntry 18}raqmonDsTotalOctetsReceived OBJECT-TYPESYNTAXCounter32UNITS"octets"MAX-ACCESSaccessible-for-notifySTATUScurrent
DESCRIPTION"The total number of payload octets (i.e., not including
header or padding octets) transmitted in packets by the
receiver within a communication session since the start
of the session."REFERENCE"Section 5.18 of [RFC4710]"::={ raqmonDsNotificationEntry 19}raqmonDsTotalOctetsSent OBJECT-TYPESYNTAXCounter32UNITS"octets"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The number of payload octets (i.e., not including headers
or padding) transmitted in packets by the sender within
a communication sub-session since the start of the
session."REFERENCE"Section 5.19 of [RFC4710]"::={ raqmonDsNotificationEntry 20}raqmonDsCumulativePacketLoss OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The number of packets from this session whose loss
had been detected since the start of the session."REFERENCE"Section 5.20 of [RFC4710]"::={ raqmonDsNotificationEntry 21}
raqmonDsPacketLossFraction OBJECT-TYPESYNTAXUnsigned32(0..100)UNITS"percentage of packets sent"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The percentage of lost packets with respect to the
overall packets sent. This is defined to be 100 times
the number of packets lost divided by the number of
packets expected."REFERENCE"Section 5.21 of [RFC4710]"::={ raqmonDsNotificationEntry 22}raqmonDsCumulativeDiscards OBJECT-TYPESYNTAXCounter32
UNITS"packets"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The number of packet discards detected since the
start of the session."REFERENCE"Section 5.22 of [RFC4710]"::={ raqmonDsNotificationEntry 23}raqmonDsDiscardsFraction OBJECT-TYPESYNTAXUnsigned32(0..100)UNITS"percentage of packets sent"MAX-ACCESSaccessible-for-notifySTATUScurrent
DESCRIPTION"The percentage of discards with respect to the overall
packets sent. This is defined to be 100 times the number
of discards divided by the number of packets expected."REFERENCE"Section 5.23 of [RFC4710]"::={ raqmonDsNotificationEntry 24}raqmonDsSourcePayloadType OBJECT-TYPESYNTAXUnsigned32(0..127)MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The payload type of the packet sent by this RDS."REFERENCE
"RFC 1890, Section 5.24 of [RFC4710] "::={ raqmonDsNotificationEntry 25}raqmonDsReceiverPayloadType OBJECT-TYPESYNTAXUnsigned32(0..127)MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"The payload type of the packet received by this RDS."REFERENCE"RFC 1890, Section 5.25 of [RFC4710] "::={ raqmonDsNotificationEntry 26}raqmonDsSourceLayer2Priority OBJECT-TYPESYNTAXUnsigned32(0..7)
MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Source Layer 2 priority used by the data source to send
packets to the receiver by this data source during this
communication session."REFERENCE"Section 5.26 of [RFC4710]"::={ raqmonDsNotificationEntry 27}raqmonDsSourceDscp OBJECT-TYPESYNTAXDscpMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Layer 3 TOS/DSCP values used by the Data Source to
prioritize traffic sent."REFERENCE"Section 5.27 of [RFC4710]"::={ raqmonDsNotificationEntry 28}raqmonDsDestinationLayer2Priority OBJECT-TYPESYNTAXUnsigned32(0..7)MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Destination Layer 2 priority. This is the priority used
by the peer communicating entity to send packets to the
data source."REFERENCE"Section 5.28 of [RFC4710]"::={ raqmonDsNotificationEntry 29}
raqmonDsDestinationDscp OBJECT-TYPESYNTAXDscpMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Layer 3 TOS/DSCP values used by the
peer communicating entity to prioritize traffic
sent to the source."REFERENCE"Section 5.29 of [RFC4710]"::={ raqmonDsNotificationEntry 30}raqmonDsCpuUtilization OBJECT-TYPESYNTAXUnsigned32(0..100)UNITS"percent"
MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"Latest available information about the total CPU
utilization."REFERENCE"Section 5.30 of [RFC4710]"::={ raqmonDsNotificationEntry 31}raqmonDsMemoryUtilization OBJECT-TYPESYNTAXUnsigned32(0..100)UNITS"percent"MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION
"Latest available information about the total memory
utilization."REFERENCE"Section 5.31 of [RFC4710]"::={ raqmonDsNotificationEntry 32}-- definitions of the notifications---- raqmonDsAppName is the only object that MUST be sent by an-- RDS every time the static notification is generated.-- raqmonDsTotalPacketsReceived is the only object that MUST be-- sent by an RD every time the dynamic notification is generated.-- Other objects from the raqmonDsNotificationTable may be-- included in the variable binding list. Specifically, a raqmon-- notification will include MIB objects that provide information-- about metrics that characterize the application session
raqmonDsStaticNotification NOTIFICATION-TYPEOBJECTS{ raqmonDsAppName }STATUScurrentDESCRIPTION"This notification maps the static parameters in the
BASIC RAQMON PDU onto an SNMP transport.
This notification is expected to be sent once per
session, or when a new sub-session is initiated.
The following objects MAY be carried by the
raqmonDsStaticNotification:
raqmonDsDataSourceDevicePort,
raqmonDsReceiverDevicePort,
raqmonDsSessionSetupDateTime,
raqmonDsSessionSetupDelay,
raqmonDsSessionDuration,
raqmonDsSourcePayloadType,
raqmonDsReceiverPayloadType,
raqmonDsSourceLayer2Priority,
raqmonDsSourceDscp,
raqmonDsDestinationLayer2Priority,
raqmonDsDestinationDscp
It is RECOMMENDED to keep the size of a notification
within the MTU size limits in order to avoid
fragmentation."::={ raqmonDsNotifications 1}raqmonDsDynamicNotification NOTIFICATION-TYPEOBJECTS{ raqmonDsTotalPacketsReceived }STATUScurrentDESCRIPTION"This notification maps the dynamic parameters in the
BASIC RAQMON PDU onto an SNMP transport.
The following objects MAY be carried by the
raqmonDsDynamicNotification:
raqmonDsRoundTripEndToEndNetDelay,
raqmonDsOneWayEndToEndNetDelay,
raqmonDsApplicationDelay,
raqmonDsInterArrivalJitter,
raqmonDsIPPacketDelayVariation,
raqmonDsTotalPacketsSent,
raqmonDsTotalOctetsReceived,
raqmonDsTotalOctetsSent,
raqmonDsCumulativePacketLoss,
raqmonDsPacketLossFraction,
raqmonDsCumulativeDiscards,
raqmonDsDiscardsFraction,
raqmonDsCpuUtilization,
raqmonDsMemoryUtilization
It is RECOMMENDED to keep the size of a notification
within the MTU size limits in order to avoid
fragmentation."::={ raqmonDsNotifications 2}raqmonDsByeNotification NOTIFICATION-TYPEOBJECTS{ raqmonDsAppName }STATUScurrentDESCRIPTION"The BYE Notification. This Notification is the
equivalent of the RAQMON NULL PDU, which signals the
end of a RAQMON session."::={ raqmonDsNotifications 3}
---- conformance informationraqmonDsCompliance OBJECTIDENTIFIER::={ raqmonDsConformance 1}raqmonDsGroups OBJECTIDENTIFIER::={ raqmonDsConformance 2}raqmonDsBasicCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities that
implement this MIB module.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but
for which we have the following compliance requirements,
expressed in OBJECT clause form in this description
clause:
-- OBJECT raqmonDsPeerAddrType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
-- OBJECT raqmonDsPeerAddr
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
"MODULE-- this moduleMANDATORY-GROUPS{ raqmonDsNotificationGroup,
raqmonDsPayloadGroup }::={ raqmonDsCompliance 1}raqmonDsNotificationGroup NOTIFICATION-GROUPNOTIFICATIONS{ raqmonDsStaticNotification,
raqmonDsDynamicNotification,
raqmonDsByeNotification }STATUScurrentDESCRIPTION"Standard RAQMON Data Source Notification group."::={ raqmonDsGroups 1}raqmonDsPayloadGroup OBJECT-GROUPOBJECTS{ raqmonDsAppName,
raqmonDsDataSourceDevicePort,
raqmonDsReceiverDevicePort,
raqmonDsSessionSetupDateTime,
raqmonDsSessionSetupDelay,
raqmonDsSessionDuration,
raqmonDsSessionSetupStatus,
raqmonDsRoundTripEndToEndNetDelay,
raqmonDsOneWayEndToEndNetDelay,
raqmonDsApplicationDelay,
raqmonDsInterArrivalJitter,
raqmonDsIPPacketDelayVariation,
raqmonDsTotalPacketsReceived,
raqmonDsTotalPacketsSent,
raqmonDsTotalOctetsReceived,
raqmonDsTotalOctetsSent,
raqmonDsCumulativePacketLoss,
raqmonDsPacketLossFraction,
raqmonDsCumulativeDiscards,
raqmonDsDiscardsFraction,
raqmonDsSourcePayloadType,
raqmonDsReceiverPayloadType,
raqmonDsSourceLayer2Priority,
raqmonDsSourceDscp,
raqmonDsDestinationLayer2Priority,
raqmonDsDestinationDscp,
raqmonDsCpuUtilization,
raqmonDsMemoryUtilization }STATUScurrentDESCRIPTION"Standard RAQMON Data Source payload MIB objects group."::={ raqmonDsGroups 2}END